Closed
Conversation
- default resource assignment to not have resource assignment - make it so individual containers have separate resource assignment
|
|
Contributor
|
Closing this PR after having an internal discussion on the issues that can be generated if we do not set resource limits to our integration |
Author
|
@juanjjaramillo I will open a separate PR for granular resource config (as I this is still necessary). Can I at least set the default requests lower than this? They are quite high for most clusters: |
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which problem is this PR solving?
There are two problems this solves:
Fixes: #853, #499
Short description of the changes
Type of change
New Tests?
n/a
Checklist: